docs(ospo): community health rollout v2 — README, agents.md, health files#425
docs(ospo): community health rollout v2 — README, agents.md, health files#425dj4oC wants to merge 1 commit into
Conversation
|
|
…iles Introduced by the Kiteworks Open Source Program Office (OSPO) on May 5, 2026. Changes: - README.md: rewritten with OSPO v2 template — license-specific migration guidance, Community & Support section, Contributing workflow, Security section pointing to security.owncloud.com + YesWeHack bug bounty - agents.md: AI agent context file with architecture, build commands, and OSPO Policy Constraints (GitHub Actions, Dependabot, Git Workflow) - CODE_OF_CONDUCT.md: redirect to https://owncloud.com/contribute/code-of-conduct/ - CONTRIBUTING.md: redirect to https://owncloud.com/contribute/ - SECURITY.md: redirect to https://security.owncloud.com + YesWeHack - SUPPORT.md: redirect to https://owncloud.com/contact-us/ + channels OSPO: https://kiteworks.com/opensource Signed-off-by: David Walter <[email protected]>
dj4oC
force-pushed
the
ospo/community-health-v2
branch
from
b94c961 to
7d190d3
Compare
Policy hit — root-directory edits. This PR adds/rewrites root-level files (README.md, agents.md, CODE_OF_CONDUCT.md, CONTRIBUTING.md, SECURITY.md, SUPPORT.md). Per this bot's operating rules, root-directory edits are never auto-processed — commenting and stopping; a maintainer must review and merge manually. Separately flagging for human attention: this PR introduces Generated by Claude Code |
| - `js/` -- Frontend JavaScript | ||
| - `css/` -- Stylesheets | ||
| - `templates/` -- PHP templates | ||
| - `tests/` -- PHPUnit tests |
There was a problem hiding this comment.
| - `tests/` -- PHPUnit tests | |
| - `tests/` -- PHPUnit and acceptance tests |
| # Test | ||
| make test-php-unit |
There was a problem hiding this comment.
| # Test | |
| make test-php-unit | |
| # Test (PHPunit) | |
| make test-php-unit | |
| # Test (API acceptance) | |
| make test-acceptance-api | |
| # Test (CLI acceptance) | |
| make test-acceptance-cli | |
| # Test (WebUI acceptance) | |
| make test-acceptance-webui | |
| ``` | ||
|
|
||
| `config:app:set encryption useMasterKey --value 1/0` | ||
| **Important:** Once enabled, encryption cannot be disabled. Read the documentation thoroughly before enabling. Requires OpenSSL 1.1.x (see repository notes regarding OpenSSL 3.x compatibility). |
There was a problem hiding this comment.
I think that this is not strictly true. IMO encryption does have an encryption disable command:
occ encryption:decrypt-all
Is that still true?
| [](LICENSE) [](https://kiteworks.com/opensource) [](https://hub.docker.com/r/owncloud/server) | ||
|
|
||
| The values bellow mostly represent internal configuration state and should not be set by the user directly. They are controlled by respective encryption-commands. Change only if you know what you are doing or are debugging. | ||
| An ownCloud Classic (OC10) app that provides transparent server-side encryption of files using AES-256 keys. Once enabled in the admin settings, all newly uploaded files are encrypted at rest. The module supports master key encryption, per-user keys, recovery keys, and optional HSM (Hardware Security Module) integration for key storage. |
There was a problem hiding this comment.
IMO per-user keys was "deprecated" (or something) in the past. I don't think that we want to recommend user-key encryption any more?
3 participants
Summary
This PR is part of the Kiteworks OSPO community health rollout (kiteworks.com/opensource), applied to all ~110 public ownCloud repositories starting May 5, 2026.
Test plan
🤖 Generated with Claude Code as part of the ownCloud OSPO rollout.
Kiteworks OSPO: https://kiteworks.com/opensource